OPC Studio User's Guide and Reference
Licenses for Redistributed Material
Your usage of the software created with elements from OPC Studio must (in addition to the terms of OPC Studio EULA) also comply with license terms of the 3rd-party material that comes with OPC Studio. For the precise license terms, see Licenses for 3rd-party Material.
Depending on the particular subset of OPC Studio elements that you redistribute or deploy with your application, the specific 3rd-party licensed material may not be included in your distribution/deployment. You only need to be concerned about the material that actually gets redistributed with your software. The table below explains which 3rd-party licensed material is needed when.
| Material | Needed When |
| 16x16 Free Application Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Diagone Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Discovery Icon Theme | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Fugue 16px Additional Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Fugue 16px Additional Icons 2 | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Fugue 16px Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Iconza Black Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Krypton software | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| SharpPcap | If your distribution contains the files of the OpcLabs.Pcap assembly. |
| PacketDotNet | If your distribution contains the files of the OpcLabs.Pcap assembly. |
| Ravenna 3D Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
| Web Mini Icons | If your distribution contains the files of the OpcLabs.BaseLibForms assembly. |
Typically, you just need to make an attribution to these somewhere in the product and/or its documentation. It always remains your responsibility, however, to comply with the precise license conditions of OPC Studio EULA and the 3rd-party material that you redistribute.
Libraries under LGPL (such as SharpPcap, PacketDotNet) have additional requirements, such as the inclusion of the license text files. We have intentionally limited the use of such libraries and make it only in separate packages that are not used by default, and that you do not have to use include, unless you specifically opt to.
When you target .NET 6+ development platform (see QuickOPC Development Platforms Differences and OPC Wizard Requirements), OPC Studio depends on (but does not ship with or include) various 3rd-party NuGet packages (mainly from Microsoft, and OPC Foundation), as described in the Licensing article. The application that you build under .NET 6+ with QuickOPC therefore needs to contain the dependency packages (and their dependencies, recursively) as well, and you must make sure such usage complies with the licensing terms of the dependency packages. When referencing the NuGet packages, you might be prompted for consent wit the dependency package licenses.
Python packages are based on the same underlying set of dependency NuGet packages. The corresponding license texts are inside each our Python package, and are referenced through standard Python mechanism.